home *** CD-ROM | disk | FTP | other *** search
-
-
-
- - 1 -
-
-
-
- 5. _B_u_g__F_i_x_e_s
-
- 5.1 _B_u_g__F_i_x_e_s__i_n__M_i_n_e_S_e_t__2_._0_1
-
- 5.1.1 _B_u_g__F_i_x_e_s__i_n__t_h_e__T_o_o_l__M_a_n_a_g_e_r
-
- +o Drill-through on binned attributes with many (>1000)
- bins could cause the Tool Manager to crash. This has
- been fixed.
-
- +o In some cases, if a DataMove server was killed by
- another datamove, the Tool Manager connected to the
- killed DataMove sometimes failed with a SIGPIPE
- exception, and more rarely with a core dump. These
- problems have been fixed.
-
- +o In some rare cases, using the edit history dialog (but
- making no changes) when the data source is a client
- file could cause spurious error messages and core
- dumps. This has been fixed.
-
- +o In the dialog for opening data files, entering a "/"
- after the file name could cause a core dump. This has
- been fixed.
-
- +o When running associations, if the table contains
- numeric columns that have been converted to strings,
- spurious error messages would be produced in version
- 2.0. This has been fixed.
-
- +o In some cases the preview column names would become
- corrupted in the SQL Query dialog. This problem has
- been fixed.
-
- +o If one added a new column, then changed the type,
- drill-through on that column would fail. This has been
- fixed.
-
- +o The "Reopen" menu option would incorrectly change the
- name of the current session. This has been fixed.
-
- +o When binning a column twice, the resulting two binned
- columns would be given the same name. Now they are
- given different names.
-
- +o Automatic binning (used for automatic slider generation
- or splatviz) would fail if the column being binned only
- had one value. This case now works correctly.
-
- +o Setting the legends for RuleViz did not work correctly
- in 2.0. This has been fixed in 2.0.1.
-
-
-
-
-
-
-
-
-
-
-
- - 2 -
-
-
-
- +o A few bugs and performance issues related to the loss
- matrix have been fixed in version 2.0.1. In version
- 2.0 when the user attempted to edit a loss matrix or
- display a lift curve, discrete values for all
- attributes were fetched from the server and cached.
- For large datasets, fetching all discrete values was
- very slow. In version 2.0.1, only values for the
- selected discrete label are fetched and cached. This
- new method speeds up fetch time considerably and
- improves the management of loss matrix and lift curve
- label value persistence.
-
- +o There was a persistence bug with bins created using
- automatic thresholds: When editing a bin loaded from a
- .mineset file the "Use Weight" toggle would always be
- set. To fix this bug it was necessary to always turn
- the toggle ON when loading a .mineset file created by
- versions prior to the final 2.01 release (including all
- beta versions of 2.01.) Hence beware: when loading an
- old .mineset file where a weight was not used for
- automatic binning, you must turn off the weight
- manually and save again.
-
- 5.1.2 _B_u_g__F_i_x_e_s__i_n__t_h_e__A_n_a_l_y_t_i_c_a_l__A_l_g_o_r_i_t_h_m_s
-
- +o The Evidence Classifier would not handle weighted
- records correctly if the Laplace correction was turned
- on. This has been fixed.
-
- 5.2 _B_u_g__F_i_x_e_s__i_n__M_i_n_e_S_e_t__2_._0
-
- 5.2.1 _G_e_n_e_r_a_l__B_u_g__F_i_x_e_s
-
- +o The precedence for expressions involving &, |, and ^
- was wrong in all tools that used expressions. It now
- correctly follows the C semantics.
-
- 5.2.2 _B_u_g__F_i_x_e_s__i_n__t_h_e__T_r_e_e__V_i_s_u_a_l_i_z_e_r
-
- +o In the previous release, bars would sometimes grow when
- highlighted. This has been fixed.
-
- +o Spotlights now always come from the same angle; they no
- longer appear horizontal when deep in the tree.
-
- +o Marks will now work correctly when binning has been
- used.
-
- 5.2.3 _B_u_g__F_i_x_e_s__i_n__t_h_e__M_a_p__V_i_s_u_a_l_i_z_e_r
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 3 -
-
-
-
- +o The "Pointer is over" message will no longer disappear
- if it is too wide for the window.
-
- 5.2.4 _B_u_g__F_i_x_e_s__i_n__t_h_e__S_c_a_t_t_e_r__V_i_s_u_a_l_i_z_e_r
-
- +o The "Pointer is over" message will no longer disappear
- if it is too wide for the window.
-
- 5.2.5 _B_u_g__F_i_x_e_s__i_n__t_h_e__R_u_l_e__V_i_s_u_a_l_i_z_e_r
-
- +o The "Pointer is over" message will no longer disappear
- if it is too wide for the window.
-
- 5.3 _B_u_g__F_i_x_e_s__i_n__M_i_n_e_S_e_t__1_._2
-
- +o The MineSet 1.2 distribution includes a patch for the
- IRIX 6.4 graphics libraries. This patch allows the Map
- Visualizer, Scatter Visualizer, and Rule Visualizer to
- correctly display text when running on remote IRIX 6.4
- systems (Octanes and Origins). Without this patch, the
- "Pointer is over" text is not displayed correctly.
-
- +o Several core dumps have been fixed.
-
- +o Several minor bug fixes not mentioned here.
-
- +o It is possible to specify in the Tool Manager that a
- column should be averaged, and then to specify that the
- Tree Visualizer should also average that column. Since
- an average of averages is usually not appropriate, a
- warning is now issued.
-
- 5.4 _B_u_g__F_i_x_e_s__i_n__M_i_n_e_S_e_t__1_._1_._1
-
- +o Highlighting graphical objects now works correctly on
- the O2. In previous versions, they would sometimes
- leave graphical remnants.
-
- +o The Scatter Visualizer legend is now correct when
- dealing with binned variables.
-
- +o Several core dumps have been fixed.
-
- +o Numerous minor bug fixes not mentioned here.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-